Replication status
The attrep_status table contains the current status of each replication task and the target data. Although updates for the tasks in the attrep_status table are generated every few seconds, The attrep_status table will only be updated after it has applied changes to the target tables. In some cases, this may take a few minutes.
| Column | Type | Description |
|---|---|---|
|
SERVER_NAME |
nvchar |
The name of the machine on which the Qlik replication server is installed. |
|
TASK_NAME |
nvchar |
The name of the Qlik data task. |
|
TASK_STATUS |
varchar |
One of the following:
Task status is FULL LOAD as long as there is at least one table in full load. After all tables have been loaded, the task status changes to CHANGE PROCESSING. |
|
STATUS_TIME |
timestamp |
When the status was last updated. |
|
PENDING_CHANGES |
int |
The number of change records that were not yet applied to the target. |
|
DISK_SWAP_SIZE |
int |
The amount of disk space that is occupied by old or offloaded transactions. |
|
TASK_MEMORY |
int |
Current memory consumption in MB. |
|
SOURCE_CURRENT_POSITION |
varchar |
The POSITION in the source endpoint that the Qlik replication server is currently reading from. |
|
SOURCE_CURRENT_TIMESTAMP |
timestamp |
The TIMESTAMP in the source from which the Qlik replication server is currently reading. Information note
The Qlik replication server aligns the timestamp read from the data source with the timestamp on the Qlik replication server machine (according to the source latency). So, for example, if the time on the source was 12:30 and the time on the Qlik replication server is 12:32, an extra two minutes will be added to the original source time. This will be the value in the SOURCE_CURRENT_TIMESTAMP column. |
|
SOURCE_TAIL_POSITION |
varchar |
The POSITION of the oldest start transaction that is still not committed. This represents the newest position that you can revert to, without losing any changes. There may, of course, be duplicates. |
|
SOURCE_TAIL_TIMESTAMP |
timestamp |
The TIMESTAMP of the oldest start transaction that is still not committed. This represents the newest TIMESTAMP that you can revert to, without losing any changes. There may, of course, be duplicates. |
|
SOURCE_TIMESTAMP_APPLIED |
timestamp |
This is the timestamp of the last transaction committed. In a bulk apply this will be the timestamp for the commit of the last transaction in that batch. It will only be changed as part of the last transaction in the batch. |